fix(tooling): align Ruff with Python 3.11#318
Conversation
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Aligns Ruff’s configured target-version with the project’s declared Python support (minimum 3.11), preventing Ruff from suggesting PEP 695 type-parameter syntax that would be invalid for the supported runtime range.
Changes:
- Set Ruff
target-versionfrompy312topy311to matchrequires-python = ">= 3.11, <3.14".
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
TypeVarform until Python 3.11 support is intentionally droppedCloses #311
Validation
ruff check .ruff format --check .(144 files already formatted)pyproject.tomlwith Pythontomllibgit diff --check